This repository has been archived by the owner on Aug 9, 2022. It is now read-only.
fix(deps): update dependency @sentry/node to v7 #121
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^6.0.0
->^7.0.0
Release Notes
getsentry/sentry-javascript
v7.9.0
Compare Source
This release adds the
tracePropagationTargets
option to the Sentry Node SDK.tracePropagationTargets
option (#5521):
as a part of gecko protocol regex group. (#4153)transpileClientSDK
option from correct location (#5516)sentry-trace
andbaggage
via root loader. (#5509)NextConfigObject
type (#5514)v7.8.1
Compare Source
distDir
value back intoindex.server.ts
(#5479)v7.8.0
Compare Source
This release adds the
transpileClientSDK
flag to the Next.JS SDK Webpack config. This option makes WebPack transpile the SDK code to the same transpilation level as the user code. By specifying this option, the Next.JS SDK works in older browsers that do not support ES6 or ES6+ (e.g. object spread) features.captureUnderscoreErrorException
argument type (#5463)eval
when checking forsentry-cli
binary (#5447)isBuild
into an exported function (#5444)_error.js
(#5378)RewriteFrames
helper value (#5445)Work in this release contributed by @mitchheddles. Thank you for your contribution!
v7.7.0
Compare Source
sentry_client
to auth headers (#5413)documentRequest
function name. (#5404)ok
responses as errors. (#5405)v7.6.0
Compare Source
This release adds the
source
field to all outgoing transactions.See the tracking GH issue for more details.
This release also re-enables lambda layer releases for the Node Serverless SDK.
Work in this release contributed by @moishinetzer. Thank you for your contribution!
v7.5.1
Compare Source
This release removes the
user_id
and thetransaction
field from the dynamic sampling context data that is attached to outgoing requests as well as sent to Relay.v7.5.0
Compare Source
This release adds the
sendDefaultPii
flag to theSentry.init
options.When using performance monitoring capabilities of the SDK, it controls whether user IDs (set via
Sentry.setUser
) are propagated in thebaggage
header of outgoing HTTP requests.This flag is set to
false
per default, and acts as an opt-in mechanism for sending potentially sensitive data.If you want to attach user IDs to Sentry transactions and traces, set this flag to
true
but keep in mind that this is potentially sensitive information.user_id
to DSC ifsendDefaultPii
istrue
(#5344)Work in this release contributed by @jkcorrea and @nfelger. Thank you for your contributions!
v7.4.1
Compare Source
This release includes the first published version of
@sentry/remix
.v7.4.0
Compare Source
This release contains the alpha version of
@sentry/remix
, our newest JavaScript SDK! For details on how to useit, please see the README and the tracking GitHub issue.
Attention: Due to an oversight, the
@sentry/remix
package is only published as part of the7.4.1
release.Work in this release contributed by @MichaelDeBoey. Thank you for your contribution!
Special thank you to @jacob-ebey for pointing us in the right direction while we were working on the Remix SDK:
https://github.com/jacob-ebey/remix-sentry.
v7.3.1
Compare Source
Work in this release contributed by @MasterOdin. Thank you for your contribution!
v7.3.0
Compare Source
_error.js
(#5259)ParseRequestOptions
to be passed to request handler (#5287)Work in this release contributed by @Arinono. Thank you for your contribution!
v7.2.0
Compare Source
showReportDialog
from NextJS SDK (#5242)@sentry/utils
(#5257)Work in this release contributed by @Arinono and @slaesh. Thank you for your contributions!
v7.1.1
Compare Source
v7.1.0
Compare Source
http
transport (#5209)dropUndefinedKeys
(#5201)debug.min
bundle variant config (#5192)handlers
module (#5190)v7.0.0
Compare Source
Version 7 of the Sentry JavaScript SDK brings a variety of features and fixes including bundle size and performance improvements, brand new integrations, support for the attachments API, and key bug fixes.
This release does not change or remove any top level public API methods (
captureException
,captureMessage
), and only requires changes to certain configuration options or custom clients/integrations/transports.Note: The v7 version of the JavaScript SDK requires a self-hosted version of Sentry 20.6.0 or higher. If you are using a version of self-hosted Sentry (aka onpremise) older than
20.6.0
then you will need to upgrade.For detailed overview of all the changes, please see our v7 migration guide.
Breaking Changes
If you are a regular consumer of the Sentry JavaScript SDK you only need to focus on the general items. The internal breaking changes are aimed at libraries that build on top of and extend the JavaScript SDK (like
@sentry/electron
or@sentry/react-native
).General
bundle.min.js
to ES6 instead of ES5. ES5 bundles are still available atbundle.es5.min.js
. (#4958)Severity
enum for bundle size reasons. Please use string literals instead. (#4926)critical
Severity level. (#5032)whitelistUrls
andblacklistUrls
have been renamed toallowUrls
anddenyUrls
in theSentry.init()
options. (#4850)BaseClient
and it's child classes now requiretransport
,stackParser
, andintegrations
to be explicitly passed in. This was done to improve tree-shakability. (#4927)@sentry/*
npm packages. See details in our migration docs.. (#4900) (#4901)Transport
API. This means custom transports will have to be adjusted accordingly..baggage
HTTP header alongsidesentry-trace
header to propogate additional tracing related information.. (#5133)registerRequestInstrumentation
export toinstrumentOutgoingRequests
in@sentry/tracing
. (#4859)UserAgent
integration toHttpContext
. (#5027)BrowserTracing
integration'smaxTransactionDuration
option withfinalTimeout
option in the@sentry/tracing
package and resetidleTimeout
based on activities count. This should improve accuracy of web-vitals like LCP by 20-30%. (#5044)@sentry/angular
to be compiled by the angular compiler. (#4641)@sentry/minimal
package in favour of using@sentry/hub
. (#4971)ignoreSentryErrors
option from AWS lambda SDK. Errors originating from the SDK will now always be caught internally. (#4994)Integrations.BrowserTracing
export from@sentry/nextjs
. Please importBrowserTracing
from@sentry/nextjs
directly.id
property fromBrowserTracing
integration.SDK_NAME
export from@sentry/browser
,@sentry/node
,@sentry/tracing
and@sentry/vue
packages. (#5040)Angular
,Ember
, andVue
integrations from@sentry/integrations
in favour of the explicit framework packages:@sentry/angular
,@sentry/ember
, and@sentry/vue
. (#4893)Status
,RequestSessionStatus
, andSessionStatus
.. Deprecated enumsSpanStatus
andSeverity
. This was done to save on bundle size. (#4891) (#4889) (#4890)@sentry/apm
package. (#4845)user
field from DSN interface.publicKey
should be used instead. (#4864)getActiveDomain
method andDomainAsCarrier
type from@sentry/hub
. (#4858)eventStatusFromHttpCode
to save on bundle size.event.stacktrace
field. (#4885)showReportDialog
method onBrowserClient
(#4973)startSpan
andchild
methods (#4849)frameContextLines
options (#4884)Sentry
from window in the Gatsby SDK (#4857)Internal
API
class from@sentry/core
.. (#4848)Session
class to use a more functional approach.. (#5054)Backend
class in favour of moving functionality into theClient
class (for more details, see #4911 and #4919).@sentry-internal/typescript
(#4940)_invokeClient
function from@sentry/hub
(#4972)@sentry/utils
(#5066)Other Changes
Features
name
field toEventProcessor
(#4932)setMeasurement
public API (#4933)Fixes
addEventListener
instrumentation (#5147)gcpfunction
(#5097)querySelector
when not available (#5160)dropUndefinedKeys
(#5163)Misc
v6.19.7
Compare Source
Work in this release contributed by @cameronaziz and @kpdecker. Thank you for your contributions!
v6.19.6
Compare Source
v6.19.5
Compare Source
v6.19.4
Compare Source
build/types
to tarballs and adjusttypes
entry points (#4824)Work in this release contributed by @MikevPeeren. Thank you for your contribution!
v6.19.3
Compare Source
v6.19.2
Compare Source
isNaN
function (#4759)v6.19.1
Compare Source
This release fixes a bug from 6.19.0 causing type import errors in most JS SDKs.
v6.19.0
Compare Source
This release makes a change to the data normalization process, limiting the number of entries or properties which will be included in any given array or object to 1000. Previously there was no limit, so in rare cases you may notice a change in your context data. If this is a problem, you can increase the limit with the new
maxNormalizationBreadth
setting. See #4689 for details.normalize
maximum properties/elements (#4689)apply
rather thancall
intry-catch
integration (#4695)@sentry/browser
(#4688)syntheticException
creation (#4691)BrowserTracing
logging flag default value (#4708)isDebugBuild
logging guard (#4696)Work in this release contributed by @Turbo87. Thank you for your contribution!
v6.18.2
Compare Source
If you are using
@sentry-internal/eslint-config-sdk
, please note that this release turns on the quotes rule to enforce usage of single quotes.This release also removes
@sentry/tracing
as a dependency of@sentry/node
. Please explicitly install and import@sentry/tracing
if you want to use performance monitoring capabilities. For more details, see our docs on setting up Node Performance Monitoring.We also now produce an ES6 version of our CDN tracing bundle, which can be accessed with
bundle.tracing.es6.min.js
.Work in this release contributed by @Ignigena. Thank you for your contribution!
v6.18.1
Compare Source
Work in this release contributed by @belgattitude, @pbernery, and @kylemh. Thank you for your contributions!
v6.18.0
Compare Source
This patch deprecates the
frameContextLines
option for the Node SDK. The migration documentation details how to migrate off the deprecatedframeContextLines
option.ignoreSentryErrors
option for AWS lambda (#4620)Work in this release contributed by @GoshaEgorian and @ichina. Thank you for your contributions!
v6.17.9
Compare Source
Work in this release contributed by @aaronadamsCA. Thank you for your contribution!
v6.17.8
Compare Source
normalizeDepth
when normalization is skipped(#4574)Work in this release contributed by @mydea. Thank you for your contribution!
v6.17.7
Compare Source
Work in this release contributed by @connorjclark. Thank you for your contribution!
v6.17.6
Compare Source
Work in this release contributed by @mobilestar1. Thank you for your contribution!
v6.17.5
Compare Source
This release deprecates the
Severity
enum, theSeverityLevel
type, and the internalSeverityLevels
array, all from@sentry/types
. In v7,Severity
will disappear (in favor ofSeverityLevel
) andSeverityLevel
andSeverityLevels
will live in@sentry/utils
. If you are using any of the three, we encourage you to migrate your usage now, using our migration guide.@sentry/webpack-plugin
to 1.18.5 (#4501)@sentry/utils
(#4492)Work in this release contributed by @Bobakanoosh and @ssnielsen. Thank you for your contributions!
v6.17.4
Compare Source
@sentry/webpack-plugin
from 1.18.3 to 1.18.4 (#4464)ExtraErrorData
'sdepth
option (#4487)BrowserTracing
integration directly (#4480)SpanStatus
enum (#4478)_isVue
not defined in Vue3 (#4461)Work in this release contributed by @7inspire, @jaeseokk, and @rchl. Thank you for your contributions!
v6.17.3
Compare Source
req
andres
if necessary when instrumenting server (#4467)v6.17.2
Compare Source
This patch contains a breaking change for anyone setting the undocumented
rethrowAfterCapture
option for@sentry/serverless
's AWS wrapper tofalse
, as its functionality has been removed. For backwards compatibility with anyone setting it totrue
(which is also the default), the option remains in theWrapperOptions
type for now. It will be removed in the next major release, though, so we recommend removing it from your code.rethrowAfterCapture
use in AWS lambda wrapper (#4448)v6.17.1
Compare Source
hidden-source-map
as webpack devtool value (#4436)Work in this release contributed by @datbth. Thank you for your contribution!
v6.17.0
Compare Source
This release contains several internal refactors that help reduce the bundle size of the SDK and help prep for our upcoming major release. There are no breaking changes in this patch unless you are using our internal
Dsn
class, which has been removed. We also deprecated a few of our typescript enums and our internalAPI
class. We've detailed in our migration documentation how to update your sdk usage if you are using any of these in your code.Work in this release contributed by @yordis, @Badisi, and @lh1me. Thank you for your contribution!
v6.16.1
Compare Source
Work in this release contributed by @KATT. Thank you for your contribution!
v6.16.0
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.